Managing updates from reference laboratories

ABSTRACT

Computerized systems, methods, and graphical user interfaces are provided to facilitate communication between physician offices and reference laboratories. A reference laboratory content manager provides a centralized conduit for interfacing clients placing orders for reference laboratory testing and reference laboratories performing testing. The reference laboratory content manager leverages centralized mapping across organizations by managing associations for procedures between reference laboratory aliases and client aliases. The centralized mapping enables the reference laboratory content manager to manage updates from reference laboratories and facilitate clients wishing to modify utilization of reference laboratories.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to commonly assigned U.S. patentapplications entitled “Facilitating Modifying Reference Laboratories”(Attorney Docket CRNI.164988) and “Leveraging Centralized MappingBetween Organizations” (Attorney Docket CRNI.164989) filed concurrentlyherewith on the same date.

BACKGROUND

Clinical reference laboratory testing plays a key role in many facets ofthe healthcare process. Many of the decisions made by healthcareproviders regarding patient care, from initial diagnosis throughtreatment and ultimate prognosis, are dictated by reference laboratorytesting. For example, approximately 80% of all diagnoses are associatedwith a reference laboratory test. Given the crucial and prevalent roleof clinical reference laboratory testing in the medical arena, it isimperative that the reference laboratory testing process provide resultsto healthcare providers in a timely and efficient manner.

While reference laboratory testing may sometimes be performed at thepoint-of-care, such as at a physician office or hospital, in many cases,the reference laboratory located at the same facility as thepoint-of-care may not be capable of performing a type of test requiredor the point-of-care location may not maintain a reference laboratory.In such cases, physical specimens collected from patients must be sentto a distant reference laboratory for testing. Currently, requestingclinical reference laboratory testing from distant referencelaboratories and disseminating results are often part of a manualprocess, which is tedious, inefficient, and error prone. For example, inthe context of a physician office requesting reference laboratorytesting for a patient, it is often difficult for the physician office todetermine an appropriate reference laboratory to perform the testing.Typically, the physician office will maintain information, such as thetesting capabilities for each of a number of reference laboratories andrecords indicating the insurance each reference laboratory accepts.Accordingly, personnel at the physician office must manually review theinformation and determine an appropriate reference laboratory.

This approach is prone to errors, such as a physical specimen being sentto a reference laboratory that is incapable of performing the testrequested and/or that does not accept the patient's insurance. In somecases, requests for reference laboratory testing may be ambiguous orincomplete from the perspective of the reference laboratory performingthe testing. For example, if a reference laboratory receives a requestto perform testing for hepatitis, the reference laboratory doesn't havesufficient information to know the specific type of hepatitis for whichto test. Accordingly, the reference laboratory may perform the incorrecttest. Alternatively, the reference laboratory may be required to contactthe requesting party (e.g., by telephone) for clarification.

Further, current reporting and tracking of reference laboratory testingresults is often not a seamless process. Results reporting is frequentlya manual process, such as through mailing, faxing, emailing, or phoningresults to the appropriate healthcare provider, providing opportunitiesfor the miscommunication of results. If a healthcare provider does notreceive results in a timely manner, the provider typically must call thereference laboratory to determine the status of the results. In cases inwhich the patient's results need to be reviewed and used for care atmultiple healthcare providers, it is typically the burden of the patientto carry the results from institution to institution.

Currently, some larger reference laboratories provide proprietarysoftware and/or hardware for entering orders for reference laboratorytesting and for accessing results. In addition, some electronic medicalrecord systems may interface with reference laboratories for order entryand result viewing. However, the software and/or hardware provided byeach reference laboratory is specific to that particular referencelaboratory. Likewise, for electronic medical record systems, individualinterfaces are required for each reference laboratory.

Because individual interfaces are required for each referencelaboratory, alias maps must be created for each reference laboratory.The alias maps provide an interface between how the physician officecodes a particular test and how each reference laboratory codes the sametest. Additional mapping must be provided to ensure a physician officereceives the results it expects for the particular test. Attributesassociated with each test provide guidance for the physician officeacquiring a specimen. There is often variance between these attributesamong reference laboratories even for the same test. Typically, aphysician office utilizes a minimum of twenty to thirty referencelaboratories to satisfy the needs of patients, insurance companies, andtesting requirements. Unfortunately, reference laboratories frequentlychange the codes associated with a given test or type of measurement.Generally, reference laboratories send out code changes once a week,often in excess of two hundred changes a month. Each time a physicianoffice receives the changes from each reference laboratory, a manualprocess is required to see how many of the code changes affect thephysician office receiving the code changes. As a result, many physicianoffices simply resort to utilizing paper. Even when the physicianoffices employ an electronic means to interface with the laboratorysoftware and/or hardware, the effort to maintain an accurate alias mapfor each reference laboratory is time consuming and costly because thereis no centralized mapping that can be leveraged between organizations.Exacerbating this problem further is that it is equally time consumingand costly to change reference laboratories should the need arisebecause new alias maps need to be created each time a physician officechanges or adds a reference laboratory.

BRIEF SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Embodiments of the present invention relate to providing a referencelaboratory network in a clinical computing environment to facilitatecommunication between physician offices and reference laboratories.Accordingly, in one aspect, an embodiment of the present invention isdirected to a method that facilitates a method of leveraging centralizedmapping between organizations. A selection of at least one referencelaboratory and a selection of procedures to be provided by each at leastone reference laboratory is received. A client order alias is receivedfrom a client for each selected procedure. A client results alias isreceived from a client for one or more expected results for eachselected procedure. An order superset is built for each selectedprocedure containing an identification of a procedure mapped to theclient order alias. A result superset is built for each procedurecontaining the identification of one or more expected results mapped tothe client results alias.

In another aspect, an embodiment of the present invention is directed toa computer system for leveraging centralized mapping betweenorganizations. The computer system comprises a processor coupled to acomputer storage medium having stored thereon a plurality of computersoftware components executable by the processor. A laboratory aliascomponent receives a laboratory order alias from at least one referencelaboratory for each provided procedure and a laboratory results aliasfor one or more results expected from each provided procedure. A clientalias component receives a client order alias from at least one clientfor each selected procedure and a client results alias for one or moreexpected results for each selected procedure. A superset componentbuilds an order superset for each selected procedure containing anetwork identification of each procedure mapped to the client orderalias and a result superset for each selected procedure containing anetwork identification of the one or more expected results mapped to theclient results alias. A namespace component builds an order namespacefor the at least one reference laboratory that includes the networkidentification of the procedure and the laboratory alias for eachprovided procedure and a result namespace for the at least one referencelaboratory that includes the network identification of the one or moreexpected results and the laboratory results alias for each providedprocedure.

In another aspect, an embodiment of the present invention is directed toa graphical user interface (GUI) to facilitate leveraging centralizedmapping between organizations. A first display area is configured todisplay a search for identifying a procedure. A second display area isconfigured to display a list of possible procedures that are responsiveto the search. A third display area is configured to display one or moreof an identification of each reference laboratory capable of performinga selected procedure, a cost associated with the selected procedure foreach reference laboratory, a turn-around-time associated with theselected procedure for each reference laboratory, and a rating for eachreference laboratory.

In another aspect, an embodiment of the present invention is directed toa method that facilitates a method of modifying reference laboratories.A request from a client to modify at least one reference laboratoryutilized by the client is received. A mapping associated with the atleast one reference laboratory to reflect the modification isautomatically updated for the client. The client is alerted that the atleast one reference laboratory has been modified.

In another aspect, an embodiment of the present invention is directed toa computer system for modifying reference laboratories. The computersystem comprises a processor coupled to a computer storage medium havingstored thereon a plurality of computer software components executable bythe processor. A modification component receives a request from a clientto modify at least one reference laboratory utilized by the client. Anautomatic modification component automatically updates a mappingassociated with the at least one reference laboratory to reflect themodification for the client. An activation component activates themodification and alerts the client that the at least one referencelaboratory has been modified.

In another aspect, an embodiment of the present invention is directed toa graphical user interface (GUI) to facilitate modifying referencelaboratories. A first display area is configured to display a list ofavailable reference laboratories. A second display area is configured todisplay a list of available procedures. A third display area isconfigured to display procedure attributes.

In another aspect, an embodiment of the present invention is directed toa method that facilitates managing updates from reference laboratories.Updates are received from at least one reference laboratory. The updatesfrom the at least one reference laboratory are mapped. The mappedupdates are communicated to at least one client. The mapped updates arecommitted.

In another aspect, an embodiment of the present invention is directed toa computer system for managing updates from reference laboratories. Thecomputer system comprises a processor coupled to a computer storagemedium having stored thereon a plurality of computer software componentsexecutable by the processor. An update component receives updates fromat least one reference laboratory. A mapping component maps the updatesfrom the at least one reference lab. A communication componentcommunicates the mapped updates to at least one client. A commitcomponent commits the mapped updates.

In another aspect, an embodiment of the present invention is directed toa graphical user interface (GUI) to facilitate leveraging centralizedmapping between organizations. A first display area is configured todisplay updates for at least one reference laboratory. A second displayarea is configured to display the mapping for the at least one referencelaboratory. A third display area is configured to display committedupdates.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The present invention is described in detail below with reference to theattached drawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitablefor use in implementing the present invention;

FIG. 2 is a block diagram showing an exemplary architecture forproviding a reference laboratory network in accordance with anembodiment of the present invention;

FIG. 3 is a flow diagram showing a method for leveraging centralizedmapping between organizations in accordance with an embodiment of thepresent invention;

FIG. 4 is a flow diagram showing a method for facilitating modifyingreference laboratories in accordance with an embodiment of the presentinvention;

FIG. 5 is a flow diagram showing a method for managing updates fromreference laboratories in accordance with an embodiment of the presentinvention;

FIG. 6 is an illustrative graphical user interface display of areference laboratory procedure search in accordance with an embodimentof the present invention;

FIG. 7 is an illustrative graphical user interface display of procedureattributes in accordance with an embodiment of the present invention;

FIG. 8 is an illustrative graphical user interface display of placing alaboratory order in accordance with an embodiment of the presentinvention; and

FIG. 9 is an illustrative graphical user interface display of procedureupdates in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies. Moreover,although the terms “step” and/or “block” may be used herein to connotedifferent components of methods employed, the terms should not beinterpreted as implying any particular order among or between varioussteps herein disclosed unless and except when the order of individualsteps is explicitly described.

Embodiments of the present invention provide computerized methods,systems, and graphical user interfaces to facilitate leveragingcentralized mapping between organizations. Embodiments of the presentinvention provide computerized methods, systems, and graphical userinterfaces to facilitate modifying reference laboratories. Embodimentsof the present invention provide computerized methods, systems, andgraphical user interfaces to facilitate managing updates from referencelaboratories. The reference laboratory network provides a centralizedconduit for maintaining a mapping of one or more reference laboratoriesorders and results to facilitate entities (i.e., clients) utilizingreference laboratory testing (e.g., hospitals, physician offices,patients, etc.), reference laboratories performing the testing, andintended recipient of testing results. The mapping allows clients toeasily build an interface with one or more reference laboratories andmanage any necessary updates. The reference laboratory network furtherallows clients to easily modify one or more reference laboratoriesutilized by the client, such as may be necessary if the client desiresto change, add, or remove a particular reference laboratory.

Referring to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, for instance, amedical information computing system, on which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 20. It will be understood and appreciatedby those of ordinary skill in the art that the illustrated medicalinformation computing system environment 20 is merely an example of onesuitable computing environment and is not intended to suggest anylimitation as to the scope of use or functionality of the invention.Neither should the medical information computing system environment 20be interpreted as having any dependency or requirement relating to anysingle component or combination of components illustrated therein.

Embodiments of the present invention may be operational with numerousother general purpose or special purpose computing system environmentsor configurations. Examples of well-known computing systems,environments, and/or configurations that may be suitable for use withthe present invention include, by way of example only, personalcomputers, server computers, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

Embodiments of the present invention may be described in the generalcontext of computer-executable instructions, such as program modules,being executed by a computer. Generally, program modules include, butare not limited to, routines, programs, objects, components, and datastructures that perform particular tasks or implement particularabstract data types. The present invention may also be practiced indistributed computing environments where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules may be located inlocal and/or remote computer storage media including, by way of exampleonly, memory storage devices.

With continued reference to FIG. 1, the exemplary medical informationcomputing system environment 20 includes a general purpose computingdevice in the form of a server 22. Components of the server 22 mayinclude, without limitation, a processing unit, internal system memory,and a suitable system bus for coupling various system components,including database cluster 24, with the server 22. The system bus may beany of several types of bus structures, including a memory bus or memorycontroller, a peripheral bus, and a local bus, using any of a variety ofbus architectures. By way of example, and not limitation, sucharchitectures include Industry Standard Architecture (USA) bus, MicroChannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronic Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus, also known as Mezzanine bus.

The server 22 typically includes, or has access to, a variety ofcomputer readable media, for instance, database cluster 24. Computerreadable media can be any available media that may be accessed by server22, and includes volatile and nonvolatile media, as well as removableand non-removable media. By way of example, and not limitation, computerreadable media may include computer storage media and communicationmedia. Computer storage media may include, without limitation, volatileand nonvolatile media, as well as removable and nonremovable mediaimplemented in any method or technology for storage of information, suchas computer readable instructions, data structures, program modules, orother data. In this regard, computer storage media may include, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVDs) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage, orother magnetic storage device, or any other medium which can be used tostore the desired information and which may be accessed by the server22. Communication media typically embodies computer readableinstructions, data structures, program modules, or other data in amodulated data signal, such as a carrier wave or other transportmechanism, and may include any information delivery media. As usedherein, the term “modulated data signal” refers to a signal that has oneor more of its attributes set or changed in such a manner as to encodeinformation in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared, and other wireless media. Combinations of any of the abovealso may be included within the scope of computer readable media.

The computer storage media discussed above and illustrated in FIG. 1,including database cluster 24, provide storage of computer readableinstructions, data structures, program modules, and other data for theserver 22.

The server 22 may operate in a computer network 26 using logicalconnections to one or more remote computers 28. Remote computers 28 maybe located at a variety of locations in a medical or researchenvironment, for example, but not limited to, clinical referencelaboratories, hospitals and other inpatient settings, veterinaryenvironments, ambulatory settings, medical billing and financialoffices, hospital administration settings, home health careenvironments, and clinicians' offices. Clinicians may include, but arenot limited to, a treating physician or physicians, specialists such assurgeons, radiologists, cardiologists, and oncologists, emergencymedical technicians, physicians' assistants, nurse practitioners,nurses, nurses' aides, pharmacists, dieticians, microbiologists,reference laboratory experts, genetic counselors, researchers,veterinarians, students, and the like. The remote computers 28 may alsobe physically located in non-traditional medical care environments sothat the entire health care community may be capable of integration onthe network. The remote computers 28 may be personal computers, servers,routers, network PCs, peer devices, other common network nodes, or thelike, and may include some or all of the components described above inrelation to the server 22. The devices can be personal digitalassistants or other like devices.

Exemplary computer networks 26 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the server 22 may include a modem or other means forestablishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin the server 22, in the database cluster 24, or on any of the remotecomputers 28. For example, and not by way of limitation, variousapplication programs may reside on the memory associated with any one ormore of the remote computers 28. It will be appreciated by those ofordinary skill in the art that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers (e.g., server 22 and remote computers 28) may be utilized.

In operation, a user may enter commands and information into the server22 or convey the commands and information to the server 22 via one ormore of the remote computers 28 through input devices, such as akeyboard, a pointing device (commonly referred to as a mouse), atrackball, or a touch pad. Other input devices may include, withoutlimitation, microphones, satellite dishes, scanners, or the like.Commands and information may also be sent directly from a remotehealthcare device to the server 22. In addition to a monitor, the server22 and/or remote computers 28 may include other peripheral outputdevices, such as speakers and a printer.

Although many other internal components of the server 22 and the remotecomputers 28 are not shown, those of ordinary skill in the art willappreciate that such components and their interconnection are wellknown. Accordingly, additional details concerning the internalconstruction of the server 22 and the remote computers 28 are notfurther disclosed herein.

Referring now to FIG. 2, a block diagram is provided illustrating anexemplary computing system architecture 200 for providing a referencelaboratory network in accordance with embodiments of the presentinvention. It will be appreciated that the computing system architectureshown in FIG. 2 is merely an example of one suitable computing systemand is not intended as having any dependency or requirement related toany single module/component or combination of modules/components.

As shown in FIG. 2, a reference laboratory content manager 202 may beprovided to coordinate, among other things, communicating orders,results, and updates between clients and reference laboratories. Thereference laboratory content manager 202 may act as a common interfaceor switch between and among multiple entities requesting referencelaboratory testing and multiple reference laboratories performing thetesting. As such, the reference laboratory content manager 202 serves asa conduit for communication of reference laboratory testing orders,results, and updates. Healthcare providers, such as hospitals, physicianoffices, and the like, may place orders for reference laboratorytesting, track the status of testing, receive results, and otherwisecommunicate with appropriate reference laboratories via the referencelaboratory content manager 202. In addition, reference laboratories mayreceive orders for reference laboratory testing and route the results tothe appropriate recipients via the reference laboratory content manager202. The reference laboratory content manager 202 manages the mappingbetween the codes utilized by reference laboratories and the codesutilized by clients, such that the clients do not have to be aware of ormaintain the mapping. The reference laboratory content manager 202manages receiving updates from the reference laboratories and determineswhich updates apply to which clients.

One or more databases, such as the database 215, may be associated withthe reference laboratory content manager 202, for storing a variety ofinformation to facilitate the mapping process. For example, the database215 may maintain information regarding the types of testing available ateach participating reference laboratory. In addition, the database 215may maintain insurance provider information for eligibility and coveragepurposes. The details and status of orders entered into the referencelaboratory content manager 202 may also be maintained in the database215. Further, the database 215 may maintain testing results and/orpointers to testing results stored at a reference laboratory's internaldatabase 242. The database may further maintain client order aliases andclient result aliases and/or pointers to such information stored at aclient's internal database 252.

As shown in FIG. 2, the reference laboratory content manager 202 may becapable of communicating with a number of different entities, such as areference laboratory 240 or a client 250 (e.g., physician office,hospital, and the like), for example, for modifying for a client theutilization of a reference laboratory, managing updates from a referencelaboratory, or leveraging centralized mapping between organizations. Itshould be noted that the entities shown communicating with the referencelaboratory content manager 202 in FIG. 2 are provided by way of exampleonly and are not intended to limit the scope of the present invention inany way. For example, a variety of other types of entities maycommunicate with the reference laboratory content manager 202. Inaddition, although only a single reference laboratory 240 and client 250are shown in FIG. 2, in operation, multiple hospitals, physicianoffices, draw stations, insurance providers, patients, and referencelaboratories may communicate with the reference laboratory contentmanager 202.

Each entity may have a computing device, such as a remote computer 28 ofFIG. 1, for communicating with the reference laboratory content manager202. In addition, communication between the reference laboratory contentmanager 202 and the various entities may be via one or more networks,which may comprise one or more wide area networks (WANs) and one or morelocal area networks (LANs), as well as one or more public networks, suchas the Internet, and one or more private networks. Further, entities maybe able to access the reference laboratory content manager 202 in avariety of ways within the scope of the present invention. For example,in some embodiments, an entity may have a native clinical computingsystem, which may interface with and be able to communicate with thereference laboratory content manager 202. In other embodiments, a clientapplication associated with the reference laboratory content manager 202may reside on an entity's computing device facilitating communicationwith the reference laboratory content manager 202. In furtherembodiments, communication may simply be a web-based communication,using, for example, a web browser to access the reference laboratorycontent manager 202 via the Internet. Any and all such variations arecontemplated to be within the scope of embodiments of the presentinvention.

In operation, an entity, such as the client 250, for example, may accessthe reference laboratory content manager 202 to enter an order forreference laboratory testing. In some cases, patients may wish to orderhis/her own reference laboratory testing and may access the referencelaboratory content manager 202 to enter an order (e.g., via a homecomputer). An order comprises a request for reference laboratory testingto be performed and may include a variety of information, such as thetype of reference laboratory testing requested, an identification of aphysical specimen, the patient, the place of collection of a physicalspecimen, the time of collection of a physical specimen, insuranceprovider information, and intended recipients of reference laboratorytesting results, for example.

An order for reference laboratory testing may be created by a useraccessing the reference laboratory content manager 202 (e.g., remotelyvia a computing device communicating with the reference laboratorycontent manager 202) and entering the order. Typically, the order willbe entered at the place the physical specimen (e.g., a blood sample,urine sample, throat swab, etc.) is collected. For example, a physicianoffice that collects a physical specimen from a patient will typicallyenter the order. However, in some cases, an order may be entered from alocation different from the place of collection. For example, aphysician office may enter an order for a patient, while the specimen iscollected from the patient at a draw station. Any and all suchvariations are contemplated to be within the scope of the presentinvention.

In some embodiments of the present invention, the reference laboratorycontent manager 202 may automatically select a reference laboratorybased on information entered via an order. For instance, the referencelaboratory content manager 202 may determine eligible referencelaboratories based on the type of test requested and referencelaboratory capability information maintained, for example, in database215. In addition, the reference laboratory content manager may utilizeinsurance provider and eligibility information to place referencelaboratory testing orders within a patient's insurance coverage.Insurance provider information may be stored by the reference laboratorycontent manager 202, for example, in the database 215. In someembodiments, the reference laboratory content manager 202 maycommunicate with insurance providers to access such information.Further, reference laboratory preferences may be established for userssuch that preferred reference laboratories are utilized if they aredetermined to be eligible. In another embodiment, the insuranceeligibility may be determined prior to submission of the sample andperformance of the test. A variety of other factors and data may beincorporated into the process of automatic reference laboratoryselection by the reference laboratory content manager 202 within thescope of the present invention.

In further embodiments of the present invention, users may specify aparticular reference laboratory for testing when entering an order. Insuch embodiments, the reference laboratory content manager 202 may beconfigured to determine whether a client-specified reference laboratoryis an eligible reference laboratory based on factors, such as referencelaboratory capabilities, insurance eligibility, and the like. In casesin which a specified reference laboratory is not an eligible referencelaboratory, the reference laboratory content manager 202 may notify theclient and provide an alternative reference laboratory.

Some types of testing and some reference laboratories necessitate uniquespecimen collection requirements. Accordingly, in some embodiments, thereference laboratory content manager 202 may maintain, for example inthe database 215, unique specimen collection requirements. The referencelaboratory content manager 202 may access and present any uniquespecimen collection requirements at the time of order placement based,for example, on the type of test requested and the selected referencelaboratory.

The reference laboratory content manager 202 may further incorporate anidentification system for identifying physical specimens andparticipating reference laboratories. For example, the referencelaboratory content manager 202 may maintain or access barcode series forreference laboratories. In addition, the system may assign each physicalspecimen a unique identification code for facilitating the associationof orders, physical specimens, and reference laboratory testing results.In some embodiments, clients may print requisitions and labels forphysical specimens at the time of order entry.

The reference laboratory content manager 202 may maintain an account foreach client entering orders and viewing results. By doing so thereference laboratory content manager 202 may group orders and resultsfor each user. Accordingly, a user may be able to access the referencelaboratory content manager 202 and view the status of pending orders andreview testing results that have been entered. As such, the referencelaboratory content manager 202 may provide one or more work queues to auser allowing the user to enter orders, track the status of pendingorders, and review entered results.

After a physical specimen is collected from a patient, it may be routedto a selected reference laboratory, such as the reference laboratory240, for testing. As indicated previously, the physical specimen may beidentified by a variety of identification means, such as use of anidentification number, barcode, or RFID tag, for example. Suchidentification allows the reference laboratory 240 to associate thephysical specimen with the appropriate order. After receiving thephysical specimen, the reference laboratory 240 performs the specifiedtesting, thereby obtaining testing results for the patient. Thereference laboratory 240 may then access the reference laboratorycontent manager 202 (e.g., via a computing device communicating with thereference laboratory content manager 202) and enter the results,associating the testing results with the appropriate order. In somecases, the reference laboratory 240 may maintain testing results in anassociated database 242 and may provide a pointer to the results to thereference laboratory content manager 202, instead of providing theactual results.

The reference laboratory content manager 202 may provide a work queue tothe reference laboratory 240, thereby allowing the reference laboratory240 to perform a variety of activities with respect to referencelaboratory testing result entry. For example, the work queue may allowthe reference laboratory 240 to view orders that are pending testingresults. In some embodiments, an alert may be provided if a testingresult has not been entered for an order within a predetermined periodof time. In addition, the work queue allows the reference laboratory 240to enter testing results or result pointers and associate the testingresults/pointers with orders.

After receiving reference laboratory testing results and/or pointers,the reference laboratory content manager 202 may store the resultsand/or pointers in an associated database, such as the database 215.Additionally, the reference laboratory content manager 202 allowsrecipients (e.g., those entities indicated in the order to receive theresults) to view the reference laboratory testing results. Results maybe communicated to recipients in a variety of ways within the scope ofthe present invention. For example, in some embodiments, the referencelaboratory content manager 202 may first provide a notification toindicated recipients that reference laboratory testing results areavailable, and recipients may then access the results. The referencelaboratory content manager may deliver such a notification to arecipient in any number of ways, such as, for example, via an electronicmail message, a message via a client application, a message via arecipient's native clinical computing system, or a generated voicerecording. In some embodiments of the present invention, the referencelaboratory content manager 202 may simply deliver the results and/orresult pointers to the recipients. The delivery of results to recipientsmay be via any number of ways within the scope of the present invention,such as for example, an electronic mail message, a client application, arecipient's native clinical computing system, a generated voicerecording, or via a fax machine.

In some embodiments of the present invention, the reference laboratorycontent manager 202 may communicate with an electronic medical record.As such, after receiving reference laboratory testing results, thereference laboratory content manager 202 may populate the testingresults into the electronic medical record. By way of example only andnot limitation, the electronic medical record may comprise a communityhealth record or personal health record.

Referring again to FIG. 2, reference laboratory content manager 202comprises a centralized mapping module 210, an updates module 220, and amodification module 230. Centralized mapping module 210 is responsiblefor leveraging centralized mapping between organizations. Updates module220 is responsible for managing updates from reference laboratories.Modification module 230 is responsible for modifying referencelaboratories.

Centralized mapping module 210 comprises laboratory alias component 211,client alias component 212, order superset component 213, resultsuperset component 214, and namespace component 215. In variousembodiments, centralized mapping module 210 includes order component216, comparison component 217, results component 218, attributecomponent 219, and state reportable component (not shown in FIG. 2).

Laboratory alias component 211 receives a laboratory order alias from atleast one reference laboratory for each provided procedure and alaboratory results alias for one or more results expected from eachprovided procedure. For example, each reference laboratory connected tothe reference laboratory content manager 202 may provide particulartests (tests, procedures, orders). Each reference laboratory may have aunique coding system already in place for each provided test. Further,each reference laboratory may have a unique set of results associatedwith each provided test. The laboratory alias component 211 collectsthis information from all connected reference laboratories.

Client alias component 212 receives a client order alias from at leastone client for each selected procedure and a client results alias forone or more expected results for each selected procedure. In oneembodiment, the client alias component presents a list of selectableclient order aliases to the client. The client selects the desiredprocedures according to their respective client order aliases and theclient alias component assigns the client results aliases based on theselection of their corresponding client order aliases. In anotherembodiment, the client alias component presents a list of selectableprocedures to the client and upon a selection of a particular procedure,the client identifies a client order alias and a client results aliasthat the client alias component retains. In one embodiment, the clientonly selects the procedures and the client order aliases and the clientresults aliases are automatically assigned, without receiving aliasesfrom the client. For example, the network identification (discussedbelow) for the order superset and the results superset may be used asthe client order alias and client results alias, respectively.

Order superset component 213 builds an order superset for each selectedprocedure containing a network identification of a procedure mapped tothe client order alias. The mapping is an association between thenetwork identification, or the particular procedure selected by theclient, and the client order alias. As noted above, in one embodiment,the client order alias is automatically assigned by the client aliascomponent when a procedure is selected by the client. The client orderalias may be the network identification itself, or it may be astandardized display name that may easily identify the order. In thisexample,

Result superset component 214 builds a result superset for each selectedprocedure containing a network identification of the one or moreexpected results mapped to the client results alias. The mapping is anassociation between the network identification for the expected resultsand the client results alias. As noted above, in one embodiment, theclient results alias is automatically assigned by the client aliascomponent when a procedure is selected by the client. The client resultsalias may be the network identification itself of the one or moreexpected results, or it may be a standardized display name that mayeasily identify the one or more expected results.

Namespace component 215 builds an order namespace for the at least onereference laboratory that includes the network identification of theprocedure and the laboratory alias for each provided procedure and aresult namespace for the at least one reference laboratory that includesthe network identification of the one or more expected results and thelaboratory results alias for each provided procedure. Thus, like theresult superset component, the namespace component builds a mapping. Themapping for the order namespace provides an association between thenetwork identification of the procedures and the laboratory alias. Themapping for the result namespace provides an association between thenetwork identification for the one or more expected results and thelaboratory results alias. As can be appreciated, any changes ormodifications that need to be made on either the client side or thereference laboratory side can be managed by the reference laboratorycontent manager 202 because the reference laboratory content manager 202coordinates and manages the mapping between all parties.

In one embodiment, order component 216 receives an order from client 240for a test. In one embodiment, comparison component 217 provides theclient with a comparison between one or more reference laboratories ofone or more of a cost, a turn-around-time, and a rating. Thisinformation allows the client, or the patient, to select the desiredreference laboratory based on the comparison. The order is typicallyidentified by the client with its client order alias. The ordercomponent passes this information along to superset order component 213.Superset order component 213 identifies the network identificationmapped to the client order alias and passes this information along tonamespace component 215. Namespace component 215 utilizes the networkidentification to identify the laboratory alias and passes the order inthe form of the laboratory alias to the reference laboratory 240.

After completing the order, reference laboratory 240 sends the resultswith the laboratory results alias to reference laboratory contentmanager 202. Namespace component 215 determines the networkidentification of the one or more expected results based on thelaboratory results alias. Namespace component 215 passes the resultsalong to the result superset component 214 along with the networkidentification of the one or more expected results. Result supersetcomponent 214 determines the client results alias associated with thenetwork identification of the one or more expected results. In oneembodiment, attribute component 219 confirms that attributes associatedwith the results match expected attributes associated with the order.For example, a particular a client making an order may expect theparticular order to return four separate items as results. Attributecomponent 219 confirms that the attributes associated with the result(i.e., four separate items) match expected attributes associated withthe order. In one embodiment, results component 218 normalizes andpresents results associated with the order to the client. In oneembodiment, the results are presented with the network identification ofthe one or more expected results. In another embodiment, the results arepresented with the client results alias as determined by result supersetcomponent 214. In another embodiment, state reportable componentcommunicates the results in real-time to the appropriate party. Forexample, state or local laws may require that certain results need to bereported to a public health agency. State reportable componentdetermines which results are subject to such laws and communicates theresults in real-time to the required party.

Updates module 220 comprises update component 221, mapping component222, communication component 223, and commit component 224. In variousembodiments, updates module 220 includes instruction component 225,automated update component 226, button component 227, alert component228, and portal laboratory component 229.

Update component 221 receives updates from at least one referencelaboratory. The updates may include details regarding the collection ofspecimens, such as collection container or tube-type, volume to becollected, method of collection, updates to acceptable ranges forresults, and the like.

Mapping component 222 maps the updates from the at least one referencelaboratory. Mapping component 222 identifies clients associated with theat least one reference laboratory and determines whether the updates arerelevant to each client. For example, an update may only affect aparticular test. If a client is associated with the at least onereference laboratory, but does not utilize the particular test, then theupdate is not relevant to that client. However, if the client doesutilized the particular test, the update is relevant to that client andmapping component 222 identifies particular items in the mapping orassociation between the client and the reference laboratory that need tobe updated. For example, attributes associated with the test may need tobe updated such that the client ordering the test needs to collect adifferent amount of specimen, or utilized a different type of container.Mapping component identifies such items.

Communication component 223 communicates the mapped updates to at leastone client. The mapped updates may identify aliases used by thereference laboratory or the client, description of the test requiringthe update, the modification to the test, whether the update has beencompleted or discarded, and the like. The mapped updates may becommunicated electronically, such as by electronic mail, fax, or throughan interface the client uses to access or utilize reference laboratorycontent manager 202.

Commit component 224 commits the mapped updates such that the updatesare applied for use by the clients. For example, if the update from thereference laboratory indicated that for a particular test a 2.0 mL of aspecimen needs to be collected using a red-top tube rather than 1.0 mLusing a yellow-top tube, once the update is committed, attributes notingthe new requirements, rather than the previous requirements, will bepresented to the client ordering the particular test.

In one embodiment, instruction component 225 provides instructions forthe at least one client to follow to commit the mapped updates. Theinstructions may allow the client to manually make the appropriatechanges to the mapping between the reference laboratory submitting theupdates and the client. These updates may alter any of the mappings orassociations discussed herein. In one embodiment, automated updatecomponent 226 commits the mapped updates without requiring furtheraction by the at least one client. In one embodiment, button component227 provides an update button for the at least one client that, whenselected, commits the mapped updates. This button allows the client toreview the updates before committing them, without requiring manualaction by the client. Both the instruction component 225 and the buttoncomponent 227 allow the client to retain control of the changemanagement process.

In one embodiment, alert component 228 alerts the at least one clientwhen an update has been committed. This may be particularly useful tohelp the client maintain an accurate record of when updates werecommitted. In one embodiment, the communication component 223 furtherprovides a list of committed updates to the at least one client. Thislist is also particularly useful to a client maintaining recordsassociated with updates.

In one embodiment, laboratory portal component provides a web-basedportal for access by the at least one reference laboratory or the atleast one client. In one embodiment, the web-based portal is configuredto receive the updates from the at least one reference laboratory andmay further provide access to review mappings pertaining to the at leastone reference laboratory and its associated clients. In anotherembodiment, the web-based portal is configured to receive a selection ofthe updates from the at least one client to be committed.

Modification module 230 comprises modification component 231, automatedmodification component 232, and activation component 233. In variousembodiments, modification module 230 includes procedure component 234,modification attribute component 235, and client portal component 236.

Modification component 231 receives a request from a client to modify atleast one reference laboratory utilized by the client. In oneembodiment, the modification is to add a new reference laboratory to amapping associated with the client. In another embodiment, themodification is to remove a reference laboratory from the mappingassociated with the client. In another embodiment, the modification isto replace a reference laboratory with another reference laboratory andthe associated mapping for the client. For example, a client may have acontract with a particular reference laboratory that is up for renewal.In many instances, it is extremely difficult to switch referencelaboratories, most often due to time, labor, and cost, if the contractnegotiation is not progressing satisfactorily. In another example, aclient may have identified a test that is not currently fulfilled by anycontracted reference laboratory and the client may need to add a newreference laboratory that can execute the test.

Automated modification component 232 automatically updates, for theclient, a mapping associated with the at least one reference laboratoryto reflect the modification. As already discussed, the mapping allowsthe reference laboratory content manager 202 to manage all connectionsbetween the clients and the reference laboratories such that the clientsnever have to learn how each reference laboratory codes a particulartest or results, and the attributes associated therewith. As can beappreciated, automated modification component 232 removes the concernsassociated with time, labor, and cost to add, remove, or replacereference laboratories because it automatically updates the mapping forthe client.

Activation component 233 activates the modification and alerts theclient that the at least one reference laboratory has been modified.Once the mapping has been properly added, removed, or switched betweenthe reference laboratory and the client, the activation componentessentially turns on the mapping so the client may begin placing andreceiving orders with the reference laboratory.

In one embodiment, procedure component 234 receives a list of proceduresfrom the client to include in the mapping. In one embodiment, procedurecomponent 234 further presents a list of selectable procedures that areavailable for the at least one reference laboratory. This allows theclient to select only the relevant procedures that the client wants toinclude in the mapping for a particular reference laboratory, ratherthan include every procedure the reference laboratory performs. Forexample, a pediatric client may not want to include procedures that areunrelated to its practice. The pediatric client can select only thoseprocedures provided by the reference laboratory that it desires toinclude in the mapping. Thus, the procedure component allows the clientto retain control of what is available in its interface to the referencelaboratory content manager 202.

In one embodiment, modification attribute component 235 presentsattributes associated with each procedure. This allows, for example, theclient to select the appropriate procedure when several relatedprocedures have attributes that indicate different sets of results areprovided. In one embodiment, each procedure from the list of proceduresincludes result types. In another example, the client is able to selectthe appropriate procedure when several related procedures haveattributes that indicate different methods of acquiring a specimen areutilized. In one embodiment, attributes include one or more of method,minimum volume, specimen collection, specimen container, specimenstorage, specimen type, specimen volume, special instructions, andtesting frequency.

In one embodiment, client portal component 235 presents a portalaccessible by the client. The portal allows the client access to thereference laboratory content manager 202 to initiate modifications orreview the mapping for the client and associated reference laboratories.

Turning now to FIG. 3, a flow diagram is provided illustrating a method300 for leveraging centralized mapping between organizations inaccordance with an embodiment of the present invention. Initially, asshown at step 310, a selection of at least one reference laboratory isreceived. For example, a physician office may have a contractualobligation to begin utilizing a new reference laboratory for particulartests. The physician office may access the reference laboratory contentmanager to set up the appropriate mapping for the particular tests forthe new reference laboratory. Accordingly, at step 320 a selection ofprocedures to be provided by each at least one reference laboratory isprovided.

At step 330, a client order alias from a client for each selectedprocedure is received. At step 340, a client results alias for one ormore expected results for each selected procedure is received. In oneembodiment, the client order alias and/or the client results alias isprovided by the reference laboratory content manager. For example, thereference laboratory content manager may provide a search screen for theclient to search for and identify tests (i.e., procedures) provided bythe reference laboratory. When the client identifies the appropriatetest in the search results, the reference laboratory content manager mayprovide an identification of the test such that, when the test isselected by the client, the identification is automatically utilized asthe client order alias. Similarly, a client results alias may also beautomatically provided by the reference laboratory content manager whenthe client selects the test. In another embodiment, the client orderalias and/or the client results alias is provided by the client suchthat the client is able to maintain a naming convention utilized by thatclient.

At step 350, an order superset is built for each selected procedurecontaining an identification of a procedure mapped to the client orderalias. The order superset provides an association between the clientorder alias and the identification of a test. As already mentioned, inone embodiment the client order alias is the identification of a test,as provided by the reference laboratory content manager. When the clientorder alias is provided by the client, such as when the client desiresto utilize a proprietary naming convention, the reference laboratorycontent manager is able to track the utilization of the client with astandard internal naming convention (i.e., the identification providedby the reference laboratory content manager) for all clients. Suchinternal tracking allows the client to add, remove, or change (i.e.,modify) reference laboratories with much less effort and cost becausethe reference laboratory content manager makes modifications to themapping without requiring the client to go through the setup processagain and identify particular tests.

Similarly, at step 360, a result superset is build for each procedurecontaining the identification of one or more expected results mapped tothe client results alias. The result superset provides an associationbetween the client results alias and the identification of one or moreexpected results for a particular test.

For example, a client may identify an electrolytes test as “Lytes”.Thus, when the client searches the reference laboratory content managerfor “Lytes”, the reference laboratory content manager may return a listcontaining tests responsive to the search. Once the client selects theappropriate test, a client order alias is received. In one embodiment,the client enters “Lytes”. The reference laboratory content manager mayidentify the selected test with the identification “123”. Accordingly,the reference laboratory content manager builds the order superset andassociates “Lytes” with “123”. The identification “123” is utilized forevery reference laboratory managed by the reference laboratory contentmanager, which allows the reference laboratory content manager to easilyprovide mapping for additional reference laboratories for the client.

Similarly, in one embodiment, the reference laboratory content managermaintains a Order-Results Relationship-Partner mapping and knows thatthe test “123” provided by the selected reference laboratory returnsresults for Na, K, Chl, and CO₂. The client may choose to identify theseresults with a client results alias. Accordingly, the referencelaboratory content manager builds the result superset to associatesodium, potassium, chloride, and CO₂ with Na, K, Chl, and CO₂,respectively.

In one embodiment, a laboratory order alias is received for eachprocedure provided by each reference laboratory. Similar to the clientorder alias, the laboratory order alias allows each reference laboratoryto maintain its own naming convention, or coding, for the procedures itprovides. In one embodiment, a laboratory results alias for one or moreresults expected from each provided procedure is received from eachreference laboratory. This allows the reference laboratory contentmanager to learn what types of results are expected for each providedprocedure from each reference laboratory. This is important to manageconsistency checking between the clients and the reference laboratoriesso that when a client makes an order, the client knows what type ofresults the order will yield, and when results are returned, thereference laboratory content manager knows if any results are missingand can immediately alert the reference laboratory.

In one embodiment, an order namespace for each at least one referencelaboratory is built that includes the identification of the procedureand the laboratory order alias for each provided procedure. The ordernamespace is the mapping between the reference laboratories and thereference laboratory content manager and is utilized in conjunction withthe order superset to determine the appropriate coding for the referencelaboratory when the client enters an order.

In one embodiment, a result namespace for each at least one referencelaboratory is built that includes an identification of the one or moreexpected results and the laboratory results alias for each providedprocedure. The result namespace is the mapping between the referencelaboratories and the reference laboratory content manager that isutilized in conjunction with the result superset to properly associatethe results returned by the reference laboratory with the client placingthe order.

In one embodiment, attributes associated with each provided procedureare received that provide context for the orders and/or results. Forexample, attributes may include one or more of method, minimum volume,specimen collection, specimen container, specimen storage, specimentype, specimen volume, special instructions, and testing frequency. Inanother example, attributes may include result types or units ofmeasure. In one embodiment, attributes associated with the results areconfirmed to match expected attributes to aid in the process ofconsistency checking, as discussed above. In one embodiment, theselected reference laboratory is alerts if the results do not matchexpected results.

In one embodiment, an order is received from the client for a procedure.In one embodiment, a list of available reference laboratories that canfulfill the order is provided. In one embodiment, the list includes oneor more of an identification of each reference laboratory, a costassociate with the order for each reference laboratory, aturn-around-time associated with the order for each referencelaboratory, and a rating for each reference laboratory. In oneembodiment, one or more results associated with the order are receivedfrom the selected laboratory. In one embodiment, the results arenormalized. In one embodiment, the normalized results are presented tothe client.

Turning now to FIG. 4, a flow diagram is provided illustrating a method400 for leveraging modifying reference laboratories, in accordance withan embodiment of the present invention. Initially, as shown at step 410,a request is received from a client to modify at least one referencelaboratory utilized by the client. In one embodiment, the requestcomprises an identification of at least one dropped reference laboratoryto drop for the client and at least one added reference laboratory toadd for the at least one client. In another embodiment, the requestcomprises an identification of at least one added reference laboratoryto add for the client. In another embodiment, the request comprises anidentification of at least one dropped reference laboratory to drop forthe client.

At step 420, a mapping associated with the at least one referencelaboratory to reflect the modification is automatically updated for theclient. In one embodiment, a list of procedures to include in themapping is received from the client. In one embodiment, the list ofprocedures is selected from a list of available procedures for the atleast one reference laboratory. For example, the client may be selectinga new reference laboratory to utilize for only certain procedures.Rather, than build a mapping for every procedure offered by the newreference laboratory, the client provides a list of or selects onlythose procedures that will be ordered at the new reference laboratory.

In one embodiment, automatically updating a mapping associated with theat least one reference laboratory to reflect the modification comprisesreceiving a list of procedures from the client. Each procedure is mappedto a code associated with the at least one reference laboratory. Asdescribed in detail above, the code may represent the referencelaboratory order or result alias and is associated with a networkidentification of the order or results. The network identification maybe any standardized identification for that particular order or results.The network identification may then be associated with a client order orresults alias to complete the base level order mapping between theclient and the reference laboratory.

In one embodiment, the list of procedures is selected by the client viaa web portal. In one embodiment, each procedure from the list ofprocedures includes attributes. In one embodiment, each procedure fromthe list of procedures further includes result types. In one embodiment,the attributes include one or more of method, minimum volume, specimencollection, specimen container, specimen storage, specimen type,specimen volume, special instructions, and testing frequency.

Turning now to FIG. 5, a flow diagram is provided illustrating a method500 for managing updates from reference laboratories, in accordance withan embodiment of the present invention. Initially, as shown at step 510,updates from at least one reference laboratory are received. The updatesmay be, for example, methodology updates, container updates, referencerange updates, and the like. At step 520, updates from the at least onereference laboratory are mapped, as described above. The mapped updatesare communicated to at least one client at step 530. The client maydesire to see what updates are available and make a determination onwhether to commit or discard the updates. At step 540, the mappedupdates are committed.

In one embodiment, an update button is provided to the client. When theupdate button is selected, or activated, the mapped updates arecommitted. In another embodiment, instructions are provided for theclient to follow to commit the mapped updates. For example, the clientmay desire to exert more control over how the updates are applied.Accordingly, the client manually commits the updates by following theprovided instructions. In one embodiment, the client accesses themapping via the portal and manually makes changes where appropriate toupdate the mapping. In this example, the client may have to manuallyadjust aliases, attributes, and the like. In one embodiment, the mappedupdates are committed without requiring further action by the at leastone client. In this example, the mapped updates are committedtransparently to the client. In one embodiment, an alert is provided tothe client when an update has been committed. In one embodiment, a listof committed updates is communicated to the client so the client isaware which updates have been committed.

In one embodiment, a web-based portal is provided for access by areference laboratory or a client. In one embodiment, the web-basedportal is configured to receive the updates from a reference laboratory.In one embodiment, the web-based portal is configured to receive aselection of updates from a client to be committed.

Referring now to FIG. 6, an illustrative screen display depicts adisplay of a reference laboratory procedure search 600, in accordancewith embodiments of the present invention. A client desiring to order aparticular procedure may first select the desired reference laboratory610. A search for a procedure name (i.e., client order alias) or networkidentification is entered in the procedure search box 620. A set ofresponsive procedures 630 is returned including both the procedurenetwork identification and the procedure name.

Referring now to FIG. 7, an illustrative screen display depicts adisplay of procedure attributes 700, in accordance with embodiments ofthe present invention. A list of procedure attributes 710 is provided toguide the client when sending a specimen to a particular referencelaboratory for a particular procedure to meet the particular referencelaboratories requirements to fulfill the particular procedure. Forexample, one or more of method, minimum volume, specimen collection,specimen container, specimen storage, specimen type, specimen volume,special instructions, and testing frequency are provided to the client.

Referring now to FIG. 8, an illustrative screen display depicts adisplay of placing a laboratory order 800, in accordance withembodiments of the present invention. A clinician desiring to order aparticular procedure searches for the procedure in the search box 805.The clinician may utilize either the procedure name or the networkidentification of the procedure. Reference laboratories 810, 820, 830providing the particular procedure are displayed. In variousembodiments, the price, turn-around-time, and rating for each referencelaboratory 810, 820, 830 are displayed so the client can place the orderwith an understanding of price, how long the test will take, and arating of the reference laboratory. This information may be relayed tothe patient so the patient can make an informed decision of whichreference laboratory should perform the test.

Referring now to FIG. 9, an illustrative screen display depicts adisplay of procedure updates 900, in accordance with embodiments of thepresent invention. A client may view the procedure updates 900 toquickly and readily assimilate the updates for a particular referencelaboratory that are applicable to the client. A code 910 identifies thereference laboratory order or results alias. A description 920identifies the network identification, in one embodiment, and the clientorder or results alias, in another embodiment. The modification 930identifies the update. The client may select to complete 940, or commit,or discard 950 the update.

As can be understood, embodiments of the present invention provide acentralized mechanism for networking entities wishing to order referencelaboratory testing with reference laboratories capable of performing thetesting. As such, embodiments of the present invention provide a conduitfor the communication of reference laboratory testing orders, results,and updates. The present invention has been described in relation toparticular embodiments, which are intended in all respects to beillustrative rather than restrictive. Alternative embodiments willbecome apparent to those of ordinary skill in the art to which thepresent invention pertains without departing from its scope.

From the foregoing, it will be seen that this invention is one welladapted to attain all the ends and objects set forth above, togetherwith other advantages which are obvious and inherent to the system andmethod. It will be understood that certain features and subcombinationsare of utility and may be employed without reference to other featuresand subcombinations. This is contemplated and within the scope of theclaims.

What is claimed is:
 1. Computer storage media having computer-executableinstructions embodied thereon that, when executed, facilitate a methodof managing updates from reference laboratories, the method comprising:receiving updates from at least one reference laboratory; mapping theupdates from the at least one reference laboratory; communicating themapped updates to at least one client; and committing the mappedupdates.
 2. The media of claim 1, wherein committing the mapped updatescomprises providing an update button for the at least one client that,when selected, commits the mapped updates.
 3. The media of claim 1,wherein committing the mapped updates comprises providing instructionsfor the at least one client to follow to commit the mapped updates. 4.The media of claim 1, wherein committing the mapped updates comprisescommitting the mapped updates without requiring further action by the atleast one client.
 5. The media of claim 1, further comprising providingan alert to the at least one client when an update has been committed.6. The media of claim 5, further comprising communicating a list ofcommitted updates to the at least one client.
 7. The media of claim 1,further comprising providing a web-based portal for access by the atleast one reference laboratory or the at least one client.
 8. The mediaof claim 7, wherein the web-based portal is configured to receive theupdates from the at least one reference laboratory.
 9. The media ofclaim 7, wherein the web-based portal is configured to receive aselection of the updates from the at least one client to be committed.10. A computer system for managing updates from reference laboratories,the computer system comprising a processor coupled to a computer storagemedium, the computer storage medium having stored thereon a plurality ofcomputer software components executable by the processor, the computersoftware components comprising: an update component for receivingupdates from at least one reference laboratory; a mapping component formapping the updates from the at least one reference laboratory; acommunication component for communicating the mapped updates to at leastone client; and a commit component for committing the mapped updates.11. The system of claim 10, further comprising an instruction componentfor providing instructions for the at least one client to follow tocommit the mapped updates.
 12. The system of claim 10, furthercomprising an automated update component for committing the mappedupdates without requiring further action by the at least one client. 13.The system of claim 10, further comprising a button component forproviding an update button for the at least one client that, whenselected, commits the mapped updates.
 14. The system of claim 10,further comprising an alert component for alerting the at least oneclient when an update has been committed.
 15. The system of claim 10,wherein the communication component further provides a list of committedupdates to the at least one client.
 16. The media of claim 1, furthercomprising a laboratory portal component for providing a web-basedportal for access by the at least one reference laboratory or the atleast one client.
 17. The media of claim 16, wherein the web-basedportal is configured to receive the updates from the at least onereference laboratory.
 18. The media of claim 16, wherein the web-basedportal is configured to receive a selection of the updates from the atleast one client to be committed.
 19. Computer storage media havingcomputer-executable instructions embodied thereon that, when executed,produce a graphical user interface (GUI) to facilitate managing updatesfrom reference laboratories, the GUI comprising: a first display areaconfigured to display updates for at least one reference laboratory; asecond display area configured to display the mapping for the at leastone reference laboratory; and a third display area configured to displaycommitted updates.
 20. The GUI of claim 19, further comprising a fourthdisplay area configured to display instructions for at least one clientto follow to commit the mapped updates.